3. New API discussion

There is a new format proposal: https://github.com/CalConnect/API/blob/master/CalendarEvent.mdwn

Some of the api issues that were discussed were

• Structured location & structured data

• Alerts and defaults support, have a separate field for defaults

• isAcknowledged — as currently is it would cause gradual expansion of alerts on the instances; solution: make isAcknowledged store not boolean but the last recurrence instance for which the alert was acknowledged, and only store it on the base range, not on the instances (unless the instance has override alerts).

• Attachments

• Multi-language support — to group localizations under a “localize” component

• Custom properties representation

  • Should we use a special prefix (like the X-)? The problem is that once use of a property is widespread enough a property’s custom name is “cut in stone”, since everyone’s using it.

  • Maybe a special string namespace/registry with easy way of claiming?

  • URLs (with domain names)?

On recurrences there was a discussion on the idea of excluding certain instances based on another event(s)

The start and end timezones are expressed through locations: first one corresponds to start, last — to end. The event timezone is independent.